chore: double zero renaming to private validium in block explorers UI and docs#48
Open
chore: double zero renaming to private validium in block explorers UI and docs#48
Conversation
API E2E Test Results207 tests 207 ✅ 18s ⏱️ Results for commit 8fb0622. ♻️ This comment has been updated with latest results. |
Unit Test Results 4 files 262 suites 9m 26s ⏱️ Results for commit 8fb0622. ♻️ This comment has been updated with latest results. |
Co-authored-by: Miguel Duarte <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What ❔
This PR aims to cover the main double-zero references in the repo to "Private Validium". Deeper changes to more risky references should be performed under further testing, The objective is to cover the main references across BE UI, meta tags and readme.
Why ❔
Checklist